fix: updated the pipeline and bicep changes #519
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request introduces new workflow files for the v2 deployment pipeline, expands support for the
dev-v3
branch in existing workflows, and updates deployment configuration to use new container registry and image naming conventions. The changes streamline the build, deployment, and cleanup processes, improve resource management, and add support for MCP Docker image builds.Workflow and CI/CD Pipeline Improvements:
.github/workflows/deploy-v2.yml
to implement a comprehensive deployment workflow for themacae-v2
branch, including quota checks, resource provisioning, deployment, e2e testing, resource cleanup, and notification steps..github/workflows/docker-build-and-push-v2.yml
to build and optionally push Docker images for backend and frontend services for themacae-v2
branch.Branch and Tag Support Enhancements:
.github/workflows/deploy.yml
and.github/workflows/docker-build-and-push.yml
to include thedev-v3
branch, and updated image tag logic to use*_v3
suffixes for relevant branches. [1] [2] [3] [4] [5]Docker Image Build Improvements:
.github/workflows/docker-build-and-push.yml
, ensuring MCP service images are included in the CI/CD pipeline.Deployment Configuration Updates:
infra/main.bicep
to use the new registry (biabcontainerreg.azurecr.io
) and standardized image naming for backend, frontend, and MCP services.availabilityZones
array to the Bastion Host module configuration ininfra/main.bicep
for improved resource deployment control.Documentation:
docs/docker_mcp_server_testing.md
to reference only the main deployment guide for troubleshooting.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information